eCatalogue meeting
Date: 19/05/2022
Participants: Cecile Guasch,Veit Jahns, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Approximate publishing date for eCatalogue: July 2022
Discuss GH 340
As part of a description of an item in a catalogue, the relationship between items has to be described.
In epo-ecat:eCatalogueLine class we have the following modifications:
-
Changing epo:hasOrderableIndicator to epo:isOrderable
-
Changing epo:hasContractedItem to epo:isContractedItem
Added the following relationships on epo:Item class with their definitions:
-
epo-ecat:hasAccessoryItem “An additional item that can enhance the original item.
WG Approval: 19/05/2022”
-
epo-ecat:hasRequiredItem “An item that is needed by another item to ensure its functionality.
Additional Information:
The item is provided without other items that are required for proper functionality.
For example, a printer cannot be used without ink cartridge; or a server cannot be used without its installation.
WG Approval: 19/05/2022”
-
epo-ecat:hasComponent “An item that is composed of another item.
Additional information:
The item is provided with its components. However, the component items may also be provided separately.
For example, a bicycle has wheels as components, but they may be provided as spare parts as well.
This relation is useful to describe different package levels of an item or hierarchies of items.
WG Approval: 19/05/2022”
-
dct:isReplacedBy “A related resource that supplants, displaces, or supersedes the described resource.
Additional information:
WG Approval: 19/05/2022”
-
dct:replaces “A related resource that is supplanted, displaced, or superseded by the described resource.
WG Approval: 19/05/2022”
-
epo-ecat:hasComplementaryItem “An item that if used with another item provides mutual enhancements to both of them.
Additional Information:
For example, gin and tonic; or smartphone and smartwatch.
WG Approval: 19/05/2022”
Discuss GH 341
-
Items in a catalogue are described usually in a textual manner. But this allows only text searches for items. If a structured search for an item with a specific property is needed, such text searches produce a lot of noise. For instance, a search for printing paper, which can be used for a laser printer. A search result might also contain laser printers itself or classification systems like GPC or ECLASS provide a property system to describe items in a structured manner. For instance, GPC has the property (here called attribute) "20000924/Type of Paper/Card" with the defined value "30011357/LASER". This allows searches for all items which have the attribute 20000924, and only those are in the search result. Similar for ECLASS. For some of these values are provided, but in other cases free values can be provided. For instance, shirt sizes (XS, S, M, etc.).
-
The proposed implementation can be done but this will add ambiguity to the model and it should be avoided.
-
Some way (meta-modelling) of expressing an arbitrary property is needed:
-
code - attribute type - a Literal not a URI
-
classification of the attribute code (GPC, ECLASS, …)
-
value as literal
-
value as reference
-
value a qualified amount
-
Actions Points
-
Propose a way to reify the relations between items (GH 340)
-
Propose a way of expressing an arbitrary property (GH 341) == eCatalogue meeting
Date: 05/05/2022
Participants: Veit Jahns
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Overall objective → Post-award and elements related to the Item.
Information regarding pre-procurement.
New technologies (blockchain, 3D printing area).
Testing data can be provided (mock-up).
Providing use cases for the eCatalogue model.
Discuss GH 317
Continuing adding definitions to epo:Item attributes:
-
*VAT category code - *this should be skipped because the requirement might change.
-
epo:hasInstockIndicator is changed to epo:isInStock to be consistent with the naming of indicators in the ontology.
-
*epo:hasExpiryDate - * is located on epo:Batch class
-
epo:BatchNumber - is replaced by predicate epo:hasID with epo:Identifier as target class.
-
In supply chain direction we might need to provide details at the manufacturer level, so we might need the role as a separate class. For the moment we can have a simple relation to the epo:Agent, epo:hasManufacturer with the following definition: “The maker of the service or product.”
-
*epo:hasNetQuantity - *relationship to epo:Quantity target class.
Task: Publish a snapshot of what has been modelled for this issue and close ticket.
Discuss GH 337
Modelling on the catalogue item price diagram.
An Item can have 0 or more than one price.
-
epo-ecat:Price was created with the following definition: “Amount of money required or given in exchange for items.”
-
epo:hasValidity changed to *epo:hasCatalogueLineValidity *for model consistency reasons.
-
epo-ecat:hasNetMonetaryValue as a predicate to epo:MonetaryValue target class.
-
epo-ecat:hasOrderableUnitFactorRate - changing the definition to the following: “The factor by which the base unit of the price can be converted to orderable unit.”
-
epo-ecat:hasQuantityThreshold - from epo-ecat:Price to epo:Quantity with the following definition: “The minimum quantity of the item that can be ordered to the given net monetary value.”
-
epo-ecat:hasLeadTime - from epo-ecat:Price to epo:Duration with the following definition: “The expected amount of time between the order and the delivery of an item.”
-
epo-ecat:hasValidityPeriod - from epo-ecat:Price to epo:Duration with the following definition: “The period of time when the item can be ordered to the given price.”
-
epo-ecat:hasDeliveryLocation - from epo-ecat:Price to epo:Duration with the following definition: “Location delivery area where the item can be ordered to the given price.”
-
*epo-ecat:hasBaseQuantity - *from epo-ecat:Price to epo:Quantity with the following definition: “The quantity at which the net monetary value applies.”
Task: Publish a snapshot of what has been modelled for this issue and close ticket.
Discuss GH 336
Proposed to add a new enumeration at-voc-new:delivery-item-type - indication whether an item is a product or a service. The dependency relationship between epo:Item and this enumeration should be epo-ecat:hasDeliveryClassification.
For instance, possible values could be:
-
SER - Trade item is a service
-
MTO - Trade item is manufactured after order
-
VQ - Trade item is variable measure item, that is, the quantity in the package is not fixed, and the price for the item varies with the quantity
-
RC - Trade item is a returnable unit
Task: Publish a snapshot of what has been modelled for this issue and close ticket.
For the next meeting we need new GH issues regarding classifications and labels of items. == eCatalogue meeting
Date: 07/04/2022
Participants: Cecile Guasch,Veit Jahns, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Discuss GH 317
Continuing adding definitions to epo:Item attributes:
-
epo:hasKeyword - we should take into consideration that this attribute should be used for the entire concept and not only for the instance; the approved definition for the moment is the following: “List of words (e.g. synonyms) to make the item searchable.
WG Approval 07/04/2022” -
epo:hasName - should have a similar definition with all the other hasName attributes in the model.
-
epo:hasExternalSpecification One option is to link this to epo:Document by using an epo:ProductSpecification class.
From a catalogue point of view we need to have a document as an abstract class which holds mainly the metadata of the document plus an additional class which models the actual binary content of that document. Examples that can be used: FRBR or DCAT.
We can use a part of DCAT for modelling the binary content of the document.
Even in DCAT, the dcat:Distribution has an URL for download and does not provide a binary format of the content.
We can further discuss the possibility of providing the binary format of the document in the ePO model.
For the moment, the epo:hasAccessURL attribute was added to epo:document class with the following definition:
“Location where the resource can be accessed.
WG Approval 07/04/2022”
Link the epo:Item class to a newly created epo:ProductSpecification class (which is an epo:Document) with the following definition:
“Document providing information about an item.
WG approval 07/04/2022”
The epo:ProductSpecification class is included in epo-ecat:eCatalogue and is modelled in the following way:
This should be further revised.
Discussing the possibility that the document might not be an epo:Document.
eCatalogue meeting
Date: 10/03/2022
Participants: Cecile Guasch, Veit Jahns, Giorgia Lodi, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Discuss GH 317
Looking at the cac:Item from UBL:
Looking at the Good Relation ontology schema: http://www.heppnetz.de/ontologies/goodrelations/goodrelations-UML.pdf
Option 1:
Creating an epo-cat:ItemInstance class where we will move the following attributes:
Option 2:
Renaming epo:ItemInstance to epo-ecat:Batch
Decision: Keep option 2.
epo:hasBestBeforeDate and epo:hasExpiryDate have different meaning (look at https://www.foodsafety.ca/blog/difference-between-best-and-expiry-dates)
Continuing discussing attributes for epo-ecat:Item class and their definitions.
-
Added definition for the new class epo-ecat:Batch: “A production lot in which the instances were produced.
WG Approval 10/03/2022” -
Added definitions for the following attributes:
-
epo:hasBestBeforeDate: “The day until which the quality of the item will remain optimal.
WG approval 10/03/2022” -
epo:hasExpiryDate: “The last day until which the item can be used.
WG approval 10/03/2021“ -
A new class epo-ecat:Brand was created to replace the epo:hasBrandName attribute with the following definition: “Name given by an organisation to its product or service, or range of products or services.
Additional Information:
Brand name allows economic operators to distinctively describe an item in their eCatalogue. This may be different from the “item name”.
WG Approval 10/03/2022” -
A new class epo-ecat:ItemModel was created to replace the epo:hasModelName attribute with the following definition: “A specific design or version of a product or service.
Additional information:
This class is meant as a reusable reference to the model name rather than as a set of specifications of an item of this particular model.
WG Approval 10/03/2022”
-
Added a new enumeration at-voc-new:unspc with a dependency link epo:hasItemClassification coming from source class epo-ecat:Item.
-
Added new definition for dependency link epo:hasItemClassification: “A classification of this item according to a specific system for classifying products or services.
Additional Information:
Examples of classification schemes are: CPV, UNSPC, eCl@ss, GPC, …
WG approval 10/03/2022”
eCatalogue meeting
Date: 24/02/2022
Participants: Cecile Guasch, Veit Jahns, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Discuss GH 317
-
Need to create a controlled vocabulary for epo:hasHazardousItemUNDGCode
-
The Manufacturer Role does not require a Situation. It’s not a Procurement Role, but a Subrelated Role.
-
We should mention that we are allowed to use more than one epo:hasID, instead of epo:hasStandardID
-
Create a diagram at the instance level:
The idea is to be able to differentiate between the Seller ID and the Manufacturer ID. We are not doing that.
We might need to align the Identifier type with Core Vocabularies and also UBL:
Option: Add multiple ID attributes for Catalogue Item class.
We should create a controlled vocabulary for epo:hasHazardousItemUNDGCode attribute, which becomes a dependency relation.
Verifying and modifying all the definitions for attributes in the Item class. Last Item is hasBrandName.
eCatalogue meeting
Date: 27/01/2022
Participants: Cecile Guasch, Veit Jahns, Giorgia Lodi, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
The work done during these eCatalogue meetings is done in the feature/model-refactoring branch.
Discuss GH 319
Presenting PEPPOL BIS model for Contact:
Add an epo:hasContactName attribute on epo:ContactPoint with the following definition:
“A short text by which a contact is known or referred to.
WG Approval 27/01/2022
”
Not in Agent, but in Contact Point to avoid:
-
Complexity on the implementation side
-
Complexity that may arise in handling the personal data and compliance to GDPR
Discuss GH 317
Item is context free, and line is contextualized.
epo-cat:CatalogueItem should not be equivalent to epo:Item.
We need to provide the possibility to:
-
Have Lot able to refer to item specification.request
-
Be able to point to a particular item from a particular retailer
We have a catalogue that refers to items.
We should create a new class called epo:ItemRequest linked to the epo:Lot; but this shall be postponed to a later development stage of the EPO.
ItemRequest is a PreAwardCatalogue (part of the Competition or eAccess phase).
Old version:
New version: deleting epo:Item and moving relations to epo:TenderLot
Added a new controlled vocabulary: epo:vat-category
Renamed eCatalogueItem to Item.
Checking attributes on epo-ecat:Item class.
Model manufacturer is a role that is played by an agent and an item has a manufacturer.
Continue working on this next meeting. == eCatalogue meeting
Date: 20/01/2022
Participants: Cecile Guasch, Veit Jahns, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre
Discuss issue #284
The type of change can be send from the provider to the receiver
We should implement this in the ontology
We can mention that there was a type of change and give the replica of the change
We need a change type code (from Veit)
Should we provide a text field where to mention what was changed
We need a description of what the catalogue action items are.
Action Code should be renamed into Change Type Code.
We can not directly interpret their wording being syntactically correct.
The action code is intended to know what and how has been changed.
We want to give the possibility that if the system wants to do the update one by one to do so.
Is it just for informing of what was changed? YES.
So it’s NOT about what should be changed.
So these are not actions, they are information.
ID of the Catalogue and of the Item stays the same. We might assume that the URI stays the same.
